home *** CD-ROM | disk | FTP | other *** search
- Path: airdmhor.gen.nz!not-for-mail
- From: gumboot@airdmhor.gen.nz (Simon Hosie)
- Newsgroups: comp.lang.c
- Subject: Re: C Uglifyer wanted
- Date: 2 Feb 1996 00:40:13 +1300
- Organization: Airdmhor
- Message-ID: <4eq8qt$66i@airdmhor.gen.nz>
- References: <47d983$aq4@apollo.ekfido.kodak.com> <DLHBy6.JJF@cix.compulink.co.uk> <4dtodp$1pf@news.chattanooga.net> <DLs1ru.9FG@ich.nl> <310CBF6F.3A17@ctrvax.vanderbilt.edu>
- NNTP-Posting-Host: localhost.gen.nz
- X-Newsreader: TIN [version 1.2 PL2]
-
- ("Dominic Monk") writes:
- > does anybody know of an useful c-code uglifyer? The code
- > should still be compilable on different platforms but
- > variable names etc. changed so that reading, editing etc,
- > becomes impossible.
-
- Marcus H. Mendenhall:
- > Just send it to the programmers who are trained in writing
- > platform-independent UNIX/Gnu (etc.) code. If has been edited for
- > any of these systems, there is no chance anyone will understand a
- > single line of it. It will have 1000+ conditional header file
- > includes and definitions, and nowhere will you be able to find the
- > little piece of code (somewgere deep inside) which actuall _does_
- > something. :-)
-
- I don't know.. the idea has potential. You could compress it as much as
- possible by taking out all the whitespace, Lempel Ziv (sp) using #defines,
- and Huffman on all of the variable and function names. It could be the
- subject of a competition for the best compression.. Lines no longer than 64
- characters, etc.
-